Obsidian Linking Workflow (Simple, Non-Messy)
Goals
- Keep notes readable
- Make every claim traceable
- Avoid broken or circular links
Core Rule: One Claim = One Link Cluster
When you make a claim, add ONE small cluster under it:
- [S:####] for source
- [D:####] for dataset
- [M:####] for method (if derived)
Example: “Trust in government dropped after 1974.” [S:0214][D:0041] (source: MASTER_DATASHEET)
Folder Roles (Do Not Mix)
- Writing:
08_Decade_Analysis/,09_Decade_Reports/,10_Case_Studies/ - Sources:
14_Data_Core/01_Evidence_Bundles/Source_Log.md - Datasets:
14_Data_Core/01_Evidence_Bundles/Dataset_Log.md - Methods:
14_Data_Core/01_Evidence_Bundles/Method_Log.md
Link Types (Obsidian)
- Use plain
file nameonly for narrative cross-links. - Never link raw data files inside the narrative text.
- Put raw data links in the logs only.
File Naming
- No renames after linking.
- If a rename is needed, update links immediately.
Claim Placement
- Claims live in narrative docs.
- Evidence lives in logs.
- Data lives in
07_Raw_Statistics/or00_Downloads_Staging/.
Suggested Minimal Frontmatter (Optional)
Ring 2 — Canonical Grounding
- Small World Networks
- Born Rule
- electric field lines can begin or end inside a region of space only when there is charge in that region
Ring 3 — Framework Connections
source_ids: [S:####, S:####] dataset_ids: [D:####] method_ids: [M:####]
Quality Pass (Weekly)
- Search for
[U]and resolve. - Spot-check 5 claims for link integrity.
- Confirm logs include URLs and access dates.
Physics/Math Special Case
- Every formula needs one source + one method note.
- If formula is adapted, note the exact change in Method_Log.
Keep It Clean
- No inline bibliographies.
- No MLA/APA.
- The logs are the citations.
Canonical Hub: CANONICAL_INDEX